Validation Issue Glossary#

Errors#

PYTHON#

These issues are generated when a Python error prevents complete validation.

ERROR:PYTHON:EXCEPTION#

Error TemplateCheckResults

Unexpected Python exception occurred. Please report this as a bug. This may or may not be due to an issue in the geodatabase, but even if it is, the issue should be accounted for by the tool and handled appropriately.

GDB#

These issues are related to some aspect of an NG911 geodatabase‘s configuration.

ERROR:GDB:MISSING_REQUIRED_DATASET#

Error TemplateCheckResults

The required feature dataset, NG911, is not present in the geodatabase.

ERROR:GDB:MISSING_REQUIRED_FEATURE_CLASS#

Error TemplateCheckResults

A required feature class is not present in the required feature dataset.

ERROR:GDB:EXTRA_ITEM#

Error TemplateCheckResults

An unexpected item, such as a feature class, was found in the geodatabase and should be removed. This code could also indicate that an item is incorrectly named.

ERROR:GDB:MISSING_DOMAIN#

Error TemplateCheckResults

A domain prescribed by the Standard has not been defined for the geodatabase.

ERROR:GDB:EXTRA_DOMAIN#

Error TemplateCheckResults

A domain not prescribed by the Standard has been defined for the geodatabase and should be removed.

ERROR:GDB:INCORRECT_DOMAIN_TYPE#

Error TemplateCheckResults

A domain is not of the correct type (coded-value or range).

ERROR:GDB:DOMAIN_MISSING_CODE#

Error TemplateCheckResults

A coded-value domain lacks an entry listed in the Standard.

ERROR:GDB:DOMAIN_EXTRA_CODE#

Error TemplateCheckResults

A coded-value domain has an entry not listed in the Standard.

ERROR:GDB:DOMAIN_CODE_VALUE_MISMATCH#

Error TemplateCheckResults

A code in a coded-value domain has an incorrect description.

ERROR:GDB:INCORRECT_DOMAIN_DESCRIPTION#

Error TemplateCheckResults

The description of a domain itself is incorrect.

DATASET#

These issues pertain to feature datasets within the geodatabase.

ERROR:DATASET:INCORRECT_SPATIAL_REFERENCE#

Error TemplateCheckResults

The spatial reference of a feature dataset is not among those allowed by the Standard.

Unused Codes#

ERROR:DATASET:MISSING_TOPOLOGY#

Error TemplateCheckResults

This code is defined but not currently used.

ERROR:DATASET:INCORRECT_TOPOLOGY#

Error TemplateCheckResults

This code is defined but not currently used.

ERROR:DATASET:TOPOLOGY_VIOLATION#

Error TemplateCheckResults

This code is defined but not currently used.

FEATURE_CLASS#

Issues in this category concern the configuration or entire contents of a particular feature class.

ERROR:FEATURE_CLASS:MISSING_REQUIRED_FIELD#

Error TemplateCheckResults

A field listed in the Standard for a particular feature class is missing.

ERROR:FEATURE_CLASS:EXTRA_FIELD#

Error TemplateCheckResults

A field not listed in the Standard for a particular feature class is present and should be removed.

ERROR:FEATURE_CLASS:INCORRECT_SPATIAL_REFERENCE#

Error TemplateCheckResults

The spatial reference of a feature class is not among those allowed by the Standard.

ERROR:FEATURE_CLASS:INCORRECT_GEOMETRY_TYPE#

Error TemplateCheckResults

The geometry type (e.g., point, polyline, polygon) of a feature class is not consistent with the Standard.

ERROR:FEATURE_CLASS:INCORRECT_FEATURE_TYPE#

Error TemplateCheckResults

The feature type (e.g., simple, annotation) of a feature class is not consistent with the Standard.

ERROR:FEATURE_CLASS:EMPTY#

Error TemplateCheckResults

The feature class contains no features.

ERROR:FEATURE_CLASS:EMPTY_SUBMISSION#

Error TemplateCheckResults

The feature class contains no features where SUBMIT = Y.

FIELD#

ERROR:FIELD:INCORRECT_FIELD_TYPE#

Error TemplateCheckResults

The data type of the field is incorrect.

ERROR:FIELD:INCORRECT_FIELD_LENGTH#

Error TemplateCheckResults

The length of the field is incorrect.

ERROR:FIELD:INCORRECT_FIELD_DOMAIN#

Error TemplateCheckResults

The field has the wrong domain assigned to it, has a domain when it should not, or has no domain when it should have one.

DOMAIN#

ERROR:DOMAIN:INVALID_VALUE#

Error FieldValuesCheckResults

The attribute is set to a value that is not present in the field’s domain.

ERROR:GENERAL:INVALID_VALUE#

Error FieldValuesCheckResults

The attribute is set to a value that is not valid for the particular feature class and field. Currently, this is only used when the TopoExcept field of ADDRESS_POINT is set to a value that only makes sense for the equivalent field in ROAD_CENTERLINE.

GENERAL#

ERROR:GENERAL:MANDATORY_IS_NULL#

Error FieldValuesCheckResults

A value in a mandatory field is null.

ERROR:GENERAL:MANDATORY_IS_BLANK#

Error FieldValuesCheckResults

A value in a mandatory field is not null, but is a blank string or similar empty value.

ERROR:GENERAL:NOT_UPPERCASE#

Error FieldValuesCheckResults

A value contains lowercase letters when all its letters should be uppercase. This is used for text fields that the Standard states should contain only all-uppercase attributes.

ERROR:GENERAL:UNIQUENESS#

Error FieldValuesCheckResults

A value is repeated in a field that should contain only unique values.

See also

Similar issues pertaining to specific cases include ERROR:NGUID:DUPLICATE, ERROR:ADDRESS:DUPLICATE, and ERROR:ADDRESS_RANGE:OVERLAP.

NGUID#

These issues pertain specifically to the validity of NGUIDs.

ERROR:NGUID:FORMAT#

Error FieldValuesCheckResults

The format of the NGUID is incorrect.

ERROR:NGUID:V2_FORMAT#

Error FieldValuesCheckResults

The format of the NGUID matches the format used by Version 2.2 of the Standard instead of the current version.

ERROR:NGUID:AGENCY#

Error FieldValuesCheckResults

The Agency ID portion of the NGUID does not exist, i.e., it is not in the AGENCYID domain.

ERROR:NGUID:LAYER#

Error FieldValuesCheckResults

The layer portion of the NGUID does not match the name of the feature class.

ERROR:NGUID:DUPLICATE#

Error FieldValuesCheckResults

The NGUID is not unique. The Local ID portion of the NGUID (and the Local_ID attribute) should be changed.

ADDRESS#

ERROR:ADDRESS:DUPLICATE#

Error FieldValuesCheckResults

An address point’s address-related fields, when combined, match those of another address point.

ADDRESS_RANGE#

ERROR:ADDRESS_RANGE:OVERLAP#

Error FieldValuesCheckResults

Address ranges of ROAD_CENTERLINE features overlap. This means that, after considering Parity_L/Parity_R there is numerical overlap between one feature’s Add_L_To or Add_R_To and another feature’s Add_L_From or Add_R_From. The features’ FullName and (as appropriate) MSAGComm_L or MSAGComm_R must also be equal for this issue to occur.

ERROR:ADDRESS_RANGE:DECREASING#

Error FieldValuesCheckResults

A ROAD_CENTERLINE feature has a from-address value greater than that side’s to-address value, i.e., Add_L_From > Add_L_To or Add_R_From > Add_L_To. Address ranges should always go from low to high.

ROAD_ESN#

ERROR:ROAD_ESN:DEVIATION#

Error FieldValuesCheckResults

A ROAD_CENTERLINE feature does one or more of the following in relation to ESZ_BOUNDARY features:

  • Passes through an intersection of ESZ polygon borders

  • Follows the border of an ESZ polygon for part, but not all, of the road’s length

ERROR:ROAD_ESN:CROSSING#

Error FieldValuesCheckResults

A ROAD_CENTERLINE feature crosses the border of one or more ESZ_BOUNDARY features. The road may have an endpoint on a border, but it may not cross a border.

ERROR:ROAD_ESN:OUT_OF_BOUNDS#

Error FieldValuesCheckResults

At least part, if not all, of a ROAD_CENTERLINE feature is neither inside an ESZ_BOUNDARY feature nor along a border.

PARITY#

These issues are related to the parity attributes of ROAD_CENTERLINE features.

Note

In this section:

  • Side refers to the left or right side of a ROAD_CENTERLINE feature

  • Parity refers to a ROAD_CENTERLINE feature’s Parity_L or Parity_R attribute

  • From-address refers to a ROAD_CENTERLINE feature’s Add_L_From or Add_R_From attribute

  • To-address refers to a ROAD_CENTERLINE feature’s Add_L_To or Add_R_To attribute

Features can have these issues on both sides. In that case, each side will have its own row in the error table.

ERROR:PARITY:EXPECTED_ZERO#

Error FieldValuesCheckResults

On a given side, the parity is ZERO, but the from-address and/or to-address is not set to 0.

ERROR:PARITY:EXPECTED_NONZERO#

Error FieldValuesCheckResults

On a given side, the parity is not ZERO, but the from-address and/or to-address is set to 0.

ERROR:PARITY:MISMATCH#

Error FieldValuesCheckResults

On a given side, the parity does not make sense given the from-address and to-address. As examples:

  • The range 101-199 could be ODD or BOTH but not EVEN or ZERO

  • The range 200-299 must be BOTH.

ERROR:PARITY:INVALID#

Error FieldValuesCheckResults

The parity is not in the PARITY domain.

ERROR:PARITY:NULL#

Error FieldValuesCheckResults

The parity is null.

LEGACY#

ERROR:LEGACY:MISMATCH#

Error FieldValuesCheckResults

A legacy attribute is not consistent with its corresponding next-gen attribute. For example, if StreetType = ROAD, then LgcyType = RD must be true.

GEOCODE#

These issues pertain to the relationship between ADDRESS_POINT and ROAD_CENTERLINE.

ERROR:GEOCODE:UNKNOWN_MATCH#

Error FieldValuesCheckResults

No ROAD_CENTERLINE feature with the given NGUID_RDCL exists.

ERROR:GEOCODE:WRONG_SIDE#

Error FieldValuesCheckResults

The RCLMatch is correct, but the RCLSide is not consistent with the address range parity on that side of the road.

ERROR:GEOCODE:BOTH_SIDES#

Error FieldValuesCheckResults

The address matches both the left and right sides of the road.

ERROR:GEOCODE:WRONG_COMMUNITY#

Error FieldValuesCheckResults

The ADDRESS_POINT feature’s MSAGComm attribute doesn’t match the ROAD_CENTERLINE feature’s MSAGComm_L (if RCLSide = LEFT) or MSAGComm_R (if RCLSide = RIGHT), but the addresses otherwise match.

ERROR:GEOCODE:OUT_OF_RANGE#

Error FieldValuesCheckResults

The ADDRESS_POINT feature’s AddNumber attribute is not within the ROAD_CENTERLINE feature’s address range on the given side.

ERROR:GEOCODE:NAME_MISMATCH#

Error FieldValuesCheckResults

The ADDRESS_POINT feature’s street name attributes do not match those of the ROAD_CENTERLINE feature.

CONSISTENCY#

ERROR:CONSISTENCY:ADDRESS_ESN#

Error FieldValuesCheckResults

The ADDRESS_POINT feature is located in an ESZ_BOUNDARY feature with a different ESN attribute.

ERROR:CONSISTENCY:ROAD_ESN#

Error FieldValuesCheckResults

The ROAD_CENTERLINE feature’s Esn_L does not match the ESN attribute of the ESZ_BOUNDARY feature on the road’s left side, or the ROAD_CENTERLINE feature’s Esn_R does not match the ESN attribute of the ESZ_BOUNDARY feature on the road’s right side.

Unused Codes#

ERROR:CONSISTENCY:COMMUNITY#

Error FieldValuesCheckResults

This code is defined but not currently used.

GEOMETRY#

ERROR:GEOMETRY:TOPOLOGY#

Error FieldValuesCheckResults

There is a topology rule violation that is not marked as an exception (using the TopoExcept field).

Warnings#

GENERAL#

WARNING:GENERAL:LEADING_TRAILING_SPACE#

Warning FieldValuesCheckResults

An attribute begins or ends with a space character.

CONSISTENCY#

WARNING:CONSISTENCY:ROAD_LEVEL#

Warning FieldValuesCheckResults

All ROAD_CENTERLINE features that intersect at a point must have the same value in their FromLevel or ToLevel attributes (as appropriate, depending on whether each feature is starting or ending at that point), unless, in reality, there is grade separation between intersecting roads, such as with a freeway overpass.

GEOMETRY#

These issues are related to the actual geometry of a feature.

WARNING:GEOMETRY:CUTBACK#

Warning FieldValuesCheckResults

A ROAD_CENTERLINE feature has a vertex with a particularly sharp angle between segments of less than 55 degrees.

WARNING:GEOMETRY:SHORT_SEGMENT#

Warning FieldValuesCheckResults

A ROAD_CENTERLINE feature has a particularly short segment of less than 5 meters.

Notices#

GDB#

NOTICE:GDB:MISSING_OPTIONAL_DATASET#

Notice TemplateCheckResults

The optional feature dataset, OptionalLayers, is missing from the geodatabase.

NOTICE:GDB:MISSING_OPTIONAL_FEATURE_CLASS#

Notice TemplateCheckResults

An optional feature class is missing from the optional feature dataset.

CONSISTENCY#

NOTICE:CONSISTENCY:ROAD_ESN#

Notice FieldValuesCheckResults

A ROAD_CENTERLINE feature lies on the border of an ESZ_BOUNDARY feature that it does not share with another ESZ feature. That is, there is an ESZ feature on one side of the road but not on the other. This Notice is only generated when ESN = 0.

On this page

This Page